According to @VitalikButerin, ZK and FHE teams should report performance as an overhead ratio—cryptographic compute time divided by raw compute time—rather than N ops/sec, enabling more hardware-independent comparisons and straightforward estimation by multiplying known raw runtimes, source: @VitalikButerin, Oct 18, 2025. He acknowledges ratios remain somewhat hardware-dependent due to heterogeneous operations, SIMD/parallelization, and memory access patterns, but argues the overhead factor is still the most informative single number for developers, source: @VitalikButerin, Oct 18, 2025. For trading due diligence on ETH rollups and privacy protocols, lower overhead ratios imply less efficiency loss versus raw compute, clarifying prover requirements and throughput planning once projects disclose these figures, supporting more comparable cross-project benchmarking, source: @VitalikButerin, Oct 18, 2025.